Remove pkg_resources runtime dependency#461
Draft
Mirochill wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
pkg_resources.resource_filename()withimportlib.resourceswhenreading the packaged phospho-SLiM data file
setuptoolsdependency that was only needed forpkg_resources, while retaining setuptools as the build backendRationale
mavisp/modules.pycurrently importspkg_resourceswhile loading packageddata. Recent setuptools installations no longer provide that module, which
prevents the MAVISp package from being used in those environments. The package
already requires Python 3.12 or newer, so the standard-library resource API can
provide the same packaged-file access without a setuptools runtime dependency.
Fixes #392
Validation
git diff --check HEAD~1..HEADpkg_resourcesreferences inmavispandpyproject.toml